Transaction Types
The value in the paymentMethods array submitted during the start operation determines what type of transaction will be initiated on the Online Payment Page. Currently, only 1 transaction can be initiated with 1 start call, meaning the array can currently only contain one element.
Value set:
EAM(Unified Data Entry Solution transaction initiation)RTP(Payment Request initiation)
An important difference is that the field validation in the request depends on this value.
For EAM paymentMethod, the terminalReference field is mandatory, while for RTP, debtorName is mandatory. Additionally, for EAM, field lengths must be measured after URL encoding, while for RTP they are measured as simple character length.
Fields:
idempotencyKey: mandatory in all cases, UUID
technicalUserId: mandatory in all cases, String
language: mandatory in all cases, enum
url: mandatory in all cases, String
transactionReference: mandatory in all cases
For EAM: length: 1-17 after URL encoding
For RTP: length: 1-17 character length
{
technicalUserId: "10234",
language: "HU",
url: "https://demo-webshop.hu",
transactionReference: "1Ffnhelta3b",
paymentMethods: [
"EAM"
],
transactionCurrency: "HUF",
transactionAmount: 250,
remittanceInfo: "Test purchase",
shopId: "shop0001",
terminalReference: "terminal0001",
timestamp: "2024-10-04T14:23:45Z",
idempotencyKey: "f4e5b92d-60ff-46bd-a26a-8342116cdec5"
}
Field lengths must be measured after URL encoding. The terminalReference is an EAM-specific field.
{
technicalUserId: "10234",
language: "HU",
url: "https://demo-webshop.hu",
transactionReference: "1Ffnhelta3b",
paymentMethods: [
"RTP"
],
transactionCurrency: "HUF",
transactionAmount: 250,
remittanceInfo: "Test purchase",
shopId: "shop0001",
debtorName: "Kovacs Bela",
timestamp: "2024-10-04T14:23:45Z",
idempotencyKey: "f4e5b92d-60ff-46bd-a26a-8342116cdec5"
}
Field lengths must be measured as simple character length. The debtorName is an RTP-specific field.
